STT 입력 개선 - #296
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 24e01182c3
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| } catch (exception: SpeechTranscriptionFailedException) { | ||
| throw exception | ||
| } catch (exception: Exception) { | ||
| throw SpeechTranscriptionFailedException("providerFailure: ${exception::class.simpleName}") |
There was a problem hiding this comment.
When the STT client throws an unexpected exception such as ResourceAccessException, this replacement exception neither retains the cause nor logs it before wrapping. The outer warning therefore reports only SpeechTranscriptionFailedException, and the global business-exception handler also omits a stack trace, so the original error message and call stack that were previously logged by the generic exception handler are lost during provider outages. Preserve the original exception as the cause or log it with its stack trace before translating it.
Useful? React with 👍 / 👎.
1 participant
Summary
inputType(TEXT/STT)을 추가하고 기본값을TEXT로 설정Testing